Add pyproject.toml #2465
Add pyproject.toml #2465
Conversation
ulgens
force-pushed
the
pyproject.toml
branch
from
87708dc to
86557ec
Compare
ulgens
force-pushed
the
pyproject.toml
branch
from
86557ec to
940b5d5
Compare
Black automatically picks up "requires-python" value from pyproject.toml, this argument is no longer needed.
ulgens
force-pushed
the
pyproject.toml
branch
from
ed27db6 to
b6eed88
Compare
| "sentry-sdk==2.49.0", | ||
| ] | ||
|
|
||
| # TODO: Consider merging with dev group |
There was a problem hiding this comment.
Yeah I think test & dev are really the same thing.
There was a problem hiding this comment.
@django/django-website How do you feel here?
| version = "0.0.1" | ||
| description = "Source code to djangoproject.com" | ||
| requires-python = ">=3.12" | ||
| classifiers = [ |
There was a problem hiding this comment.
Probably don't need these. They're for pypi metadata only I think.
There was a problem hiding this comment.
The biggest usecase is PyPI metadata but I think they are useful for communicating what is supported. Can also be used for generating badges: https://shields.io/badges/py-pi-versions-from-framework-classifiers
Python classifiers are pushed by the default pyproject-fmt setup. It can be disabled, but I see no harm.
I can remove them, there is not much benefit, but I'm on the side of keeping them documentation/communication purposes.
|
There is already a conflict with |
2 participants
Coming from #2321 (comment)
This PR handles
I preferred
exportoverpip compile. It doesn't seem there are any functional differences between two approaches, it just felt more uv-native.It seems we can't use hashes. With hashes,
pip installfails withI also made use of uv-pre-commit hook to ensure output files are always synchronized with the pyproject.toml file.
Overall, the PR introduces a new pyproject.toml based setup for managing dependencies and project settings, without breaking the existing tooling built on
requirements/folder.